Configuring Access to External Web services |
|
Before you begin this task:
- Deploy the UDDI Application.
- Create the UDDI Service Container.
- You must have the role of UDDI Administrator.
External Services Configuration enables you to specify which credentials to use for invoking the external webservice and change the service end point if required.
- On CUSP > My Applications, click
(External Services Configuration). The External Services Configuration window appears and lists all the Web service interfaces with UDDI, as their implementation class type. - Select a Web service interface from the Web Service Interface drop-down list. The Endpoints, Operations, Roles, and Properties appear in their respective panes.
- In the Roles pane, select a role for which credentials are to be specified. Only functional roles are displayed. Related properties are displayed in the Properties pane.
- In the Properties pane, select Authentication Type from the drop-down list and assign credentials in the User Name and Password fields.
Note:
- The authentication types supported are Basic, Digest, NTLM, or SAML 1.1/Basic. In case of Basic authentication, the server authorizes a request only if it can validate the user name and password for that request. Digest authentication is similar to Basic but the difference is that the password is not sent in clear text. NTLM is an authentication protocol used in various Microsoft network protocol implementations. The SAML 1.1/Basic authentication combines Basic authentication and SAML 1.1. This is typically used when integrating with the Process Platform Process Factory. SAML is the Security Assertion Markup Language open standard as defined by OASIS.
With this the UDDI service container will handle the retrieval and refresh of SAML assertions from the remote system. SAML 1.1 is used to authenticate at the remote system, this is done with the provided username and password here or in the Personal External Access.
- For Process Platform Process Factory (CPF) Web Services, SAML 1.1/Basic is the authentication mechanism to be used.
- The SAML 1.1/Basic authentication protocol implementation is not generically usable for integrations using SAML 1.1.
- Since credentials are specified at role level, different roles can use different credentials.
- You need not select a role to modify the service URL implying that the service endpoint change is not at role level.
- The authentication types supported are Basic, Digest, NTLM, or SAML 1.1/Basic. In case of Basic authentication, the server authorizes a request only if it can validate the user name and password for that request. Digest authentication is similar to Basic but the difference is that the password is not sent in clear text. NTLM is an authentication protocol used in various Microsoft network protocol implementations. The SAML 1.1/Basic authentication combines Basic authentication and SAML 1.1. This is typically used when integrating with the Process Platform Process Factory. SAML is the Security Assertion Markup Language open standard as defined by OASIS.
- Click Save button.
Tip:
If you intend to edit the XML directly instead of using the UI, click the Edit XML button and make the necessary changes.
Note:
Select the Apply to All Interfaces option to apply a customization (made for an Endpoint URL) to all the Web service interfaces, that point to the same Endpoint URL. This will avoid the need of customizing every Web service interface.